Communicating a Network Event

ABSTRACT

An Agent Apparatus is described including a Detecting Device for detecting the execution of an automated function within a communication network. The Agent Apparatus further includes a Type Determining Device for determining the type of the automated function and a Writing Device for writing information representing the type of the automated function in a predefined storage area of a record carrier.

TECHNICAL FIELD OF THE INVENTION

The present invention relates to the technical field oftelecommunication networks and to handling of events in a communicationnetwork. In particular the present invention relates to a method fordetecting employing an automated function, to an Agent Apparatus, to amethod for detecting in a Management Apparatus employing an automatedfunction, to a Management Apparatus, to a computer-readable medium forcontrolling at least one of the methods, to a data structure, to arecord carrier and to a use of an object according to the 3GPP standardTS 32.662 for storing a type of an employed automated function.

BACKGROUND OF THE INVENTION

Automated network functions may allow implementing tasks of a networkmanagement system into a communication network. Automated functions mayallow self-organization functionality of the network such asself-configuration, self-optimization, self-healing and/or automatedsoftware management. The plurality of automated functionalitiesimplemented in a network may be called “self-X” functionalities. Theself-X functionalities may allow reducing the OPEX (OperationalExpenditure) for operating and maintaining a network (OAM, OperationAdministration Maintenance), in particular for a telecommunicationnetwork or a cellular network. Network elements supporting self-Xfunctionalities may perform tasks which usually are performed bymanagement applications or human OAM operators.

Self-X functionalities however may also reduce the transparency of anetwork for a network operator. The operator may not get informationabout activities happening inside the network, since the network may beorganized using the self-X functionalities or may be managed by self-Xfunctionalities. Thus, the operator may be kept in the “dark” about whatmay actually happen inside the network or about what happened while aself-X functionality may have been employed or executed. The networkoperator may only receive indications that data in a network may havebeen changed. In an example the network operator may receive anindication that data, which may be mirrored in a database, such as a MIB(Management Information Base) of a Network Management Centre (NMC), maybe created, changed or deleted. Generating or mirroring the data mayonly provide raw data without transmitting any content or impact of theexecuted functions. Thus, an operator or Network Management System(NMS), which should know the status of the network may be more or lessonly informed about the fact that something may have happened within thenetwork but not what happened.

The document 3GPP (3rd Generation Partnership Project) TS 32.302, “3rdGeneration Partnership Project, Technical Specification Group Servicesand System Aspects, Telecommunication Management, ConfigurationManagement (CM), Notification Integration Reference Point (IRP),Information Service (IS)”, Release 8, V8.0.0, 2008-12, may define aninterface through which an IRPManager can subscribe to an IRPAgent forreceiving notification.

The document 3GPP TS 32.662, “3rd Generation Partnership Project,Technical Specification Group Services and System Aspects,Telecommunication Management, Configuration Management (CM), Kernel CMInformation Service (IS)”, Release 8, V8.0.0, 2008-16 may defineIntegration Reference Point (IRP) through which an “IRPAgent”, forexample an Element Manager (EM) or a Network Element (NE) cancommunicate configuration management related information to one orseveral “IRPManagers”, for example network managers.

The document 3GPP TS 32.663, “3rd Generation Partnership Project,Technical Specification Group Services and System Aspects,Telecommunication Management, Configuration Management (CM), Kernel CMIntegration Reference Point (IRP)”, Common Object Request BrokerArchitecture (CORBA), Solution Set (SS)”, Release 8, V8.0.0, 2008-12,may define the mapping of the Kernel CM IRP:IS to protocol specificdetails necessary for implementing this IRP in a CORBA/IDL (InterfaceDefinition Language) environment.

The document 3GPP TS 32.665, “3rd Generation Partnership Project,Technical Specification Group Services and System Aspects,Telecommunication Management, Configuration Management (CM), Kernel CMIntegration Reference Point (IRP), eXtensible Markup Language (XML)definitions”, Release 8, V8.0.0, 2008-12 may specify the XML definitionsfor the Kernel CM Integration Reference Point (IRP) as it may apply tothe interface Itf-N.

The document 3GPP TS 32.502, “3rd Generation Partnership Project,Technical Specification Group Services and System Aspects,Telecommunication Management, Self-Configuration of Network ElementIntegration Reference Point (IRP), Information Service (IS)”, Release 8,V8.0.0, 2008-12 may define Information Service (IS) part of aSelf-Configuration IRP (SCIRP).

In the document 3GPP TS 32.503, “3rd Generation Partnership Project,Technical Specification Group Services and System Aspects,Telecommunication Management, Self-Configuration of Network ElementIntegration Reference Point (IRP), Common Object Request BrokerArchitecture (CORBA) Solution Set (SS)”, Release 8, V8.0.0, 2008-12 aCORBA solution set of software management IRP may be described for anIRP whose semantics may be specified in software management IRPinformation service.

The document 3GPP TS 32.532, “3rd Generation Partnership Project,Technical Specification Group Services and System Aspects,Telecommunication Management, Software Management Integration ReferencePoint (IRP), Information Service (IS)”, Release 8, V8.0.0, 2008-12, maydescribe a software management interface IRP information service.

The document 3GPP TS 32.533, “3rd Generation Partnership Project,Technical Specification Group Services and System Aspects,Telecommunication Management, Software Management Integration ReferencePoint (IRP), Common Object Request Broker Architecture (CORBA) SolutionSet (SS)”, Release 8, V8.0.0, 2008-12, may describe a CORBA solution setof software management IRP for an IRP whose semantics may be specifiedin software management IRP information service.

There may be a need to provide a more efficient network management.

SUMMARY OF THE INVENTION

According to an exemplary embodiment of the present invention, a methodfor detecting employing of an automated function, an Agent Apparatus, amethod for detecting in a Management Apparatus employing of an automatedfunction within a communication network, a Management Apparatus, acomputer-readable medium, a program element, a data structure, a recordcarrier, and a use of an object according to the 3GPP standard TS 32.662for storing a type of an automated function may be provided.

According to an exemplary embodiment of the present invention, a methodfor detecting employing an automated function may be provided. In anexample the method may comprise detecting the execution of an automatedfunction within a communication network, determining the type of theautomated function and writing information representing the type of theautomated function in a predefined storage area of a record carrier ordata structure. In an example the end of the execution of an automatedfunction may be detected.

According to another exemplary embodiment of the present invention, anAgent Apparatus, comprising a Detecting Device, a Type DeterminingDevice and a Writing Device may be provided. The Detecting Device may beadapted for detecting the execution of an automated function within acommunication network. In an example the Type Determining Device may beadapted for determining the type of an executed automated function andthe Writing Device may be adapted for writing information representingthe type of the automated function in a predefined storage area of arecord carrier.

In an example, writing information representing the type of theautomated function may comprise creating an object, deleting an objectand/or changing an object. An object in an example may be a managedobject. In a further example writing a type of an automated function maycomprise using a notifyObjectCreation method, using anotifyObjectDeletion method and/or using a notifyAttributeValueChangemethod.

The concept of creating, deleting and/or changing Managed Objects mayallow communicating between an Agent Apparatus and a ManagementApparatus. In other words, the Agent Apparatus may write, delete and/orchange values at predefined storage areas of a record carrier. Thus, aManagement Apparatus may access these predefined storage areas in orderto read-out corresponding values. In order to inform the ManagementApparatus about creation, deletion and/or change of the managed objectsan Agent Apparatus may use a corresponding method and/or message, e.g. anotifyObjectCreation method, a notifyObjectDeletion method and/or anotifyAttributeValueChange method.

Creating a Managed Object may comprise structuring an unstructuredrecord carrier with an address scheme, e.g. by an object definition.Having an agreed object model between the Agent Apparatus and theManagement Apparatus may allow communicating the Agent Apparatus withthe Management Apparatus by accessing corresponding parameter. Thus, inan example the addressing structure or the address scheme for the recordcarrier may substantially only exist during the existence of a ManagedObject.

According to yet another exemplary embodiment of the present invention,a method for detecting in a Management Apparatus employing an automatedfunction within a communication network may be provided. The detectingmethod may comprise reading-out information representing the type of theautomated function of a predefined storage area of a record carrier anddetermining the employment of an automated function using the read-outinformation.

In an example, the method for detecting employing an automated functionor detecting the employment of an automated function may comprisedetecting the execution of an automated function, e.g. by receiving acorresponding message. The message or a method corresponding to themessage may be a list of parameters or an interface. The interface couldbe an Itf-N interface.

According to another exemplary embodiment of the present invention, aManagement Apparatus may be provided. The Management Apparatus maycomprise a Reading Device for reading-out information, which informationmay represent the type of the executed automated function. Theinformation may be read-out from a predefined storage area of a recordcarrier. Furthermore the Management Apparatus may comprise a DeterminingDevice, which may be adapted for determining employing an automatedfunction using the information, which may have been read-out. Thus, theread-out information may provide information to the Determining Device,which information may allow for determining that an automated functionmay have been employed or executed.

In an example, the Reading Device may be adapted for detecting theexecution of an automated function, e.g. by receiving a correspondingmessage, e.g. a notification message or an alarm message.

According to yet another exemplary embodiment of the present invention,a computer-readable medium may be provided comprising program code,which program code, when being executed on a processor may be adapted tocarry out at least one method of the inventive method for detectingemploying an automated function within a communication network and themethod for detecting in a Management Apparatus employing an automatedfunction within a communication network.

According to another exemplary embodiment of the present invention, adata structure may be provided which may base on the 3GPP TS 32.662standard. The data structure may comprise a parameter for storing withina network a type of an executed automated function and the parameter maybe addressable by an address scheme based on an object definition. Theobject definition may allow controlling a Reading Device such to allowthe Reading Device to find information associated with the parameterstored in a data structure, and more particularly on a record carrierdescribed or structured by the data structure. In an example the datastructure may be an object model.

According to another exemplary embodiment of the present invention, arecord carrier may be provided, wherein the record carrier may comprisea storage area e.g. a register for storing a type of an executedautomated function. The automated function may have been executed withinthe network and may be the cause for an amended network configuration.The storage area may be addressable by an address scheme based on anobject definition or on an object model. In other words, the objectdefinition may allow addressing a physical storage area such that adesired parameter can be accessed. Thus, the object model may allowpositioning a Reading Device and/or a Writing Device to an appropriatestorage area of the record carrier. The storage area may be a storingunit in a physical memory.

Examples for a record carrier and/or for a computer-readable medium maybe a floppy disk, a hard disk, a USB (Universal Serial Bus) StorageDevice, a RAM (Random Access Memory), a ROM (Read Only Memory) or anEPROM (Erasable Programmable Read Only Memory). A computer-readablemedium may also be a data communication network, e.g. the internet,which may allow downloading a program code.

According to another exemplary embodiment of the present invention, aprogram element may be provided, which when being executed by aprocessor may be adapted to carry out at least one of the inventivemethods for detecting employing an automated function within acommunication network and a method for detecting in a ManagementApparatus the employment of an automated function within a communicationnetwork.

In a self managed network, the execution of a network management taskmay be triggered by an automated function or by an automatedfunctionality, in particular by a self-X functionality within a network.This self-X functionality, automated function or automated functionalitymay comprise rearranging and reconfiguring of network elements in orderto adapt the network to a changed situation. The execution of a self-Xfunctionality may comprise creation of a corresponding Managed Object.

Changing a network configuration may have different reasons. The reasonmay be a configuration reason, an optimization reason, a healing reasonor an automated software management reason. In other words, the networkitself may react to amended conditions, such as added network nodes, toamended software versions, to failures and the network may try to copewith the amended situation by itself. Such automated behaviour or self-Xfunctionality may reduce the workload of a network operator who may beresponsible for keeping the network alive.

In a self managed network or in a network having self-X functionalitiesa control circuit, a closed loop or an open loop control may exist forregulating respectively controlling the self-X functionality. Aself-managed network, in particular the control circuit, may comprise ameasurement apparatus which may be adapted for measuring additionalparameters of the network. The self-managed network may also comprisepredefined messages exchanged between the network elements (NE), in acase, where the self-x functionalities may be distributed over somelocally separated NEs. This may be called a distributed or decentralizedarchitecture. The messages may be exchanged between the NEs, inparticular the NEs having self-X functionalities, and the messages maybypass an interface (e.g. Itf-N) to a management system. Thus, themanagement system may substantially not be involved in executing self-Xfunctionalities.

The measurements may be executed in real-time and/or statistically. Forgathering statistical measurements, data such as measurement values maybe collected over a predefined period of time and evaluated. The datamay be used in order to determine progressions of curves relating tousing resources or to determine statistics relating to using resources.The data may be gathered over a period of a day, of a week or of amonth. The measurement values are generated by sampling the value ofinterest, e.g. the use of a resource, in regular time intervals. Thevalue of interest may be sampled in a raster of 15 minutes.

In a self-X network control circuit, apparatuses may exist, which may beadapted for setting up a value range, within which value range theself-X functions may be allowed to decide on their own about choosingpredefined parameter. The control apparatuses may be also allowed toinfluence the time behavior of the self-X function within a predefinedparameter range.

However, handling reconfiguration by the network or reacting to faultscenarios by the network may leave the operator “in the dark” aboutwhat's going on inside the network. Thus, the operator may not have allinformation required for identifying the actual status of the network.Therefore, self-X functionalities could make the network intransparentfor a network operator. There may not be a possibility to identify whichof the changes in the network may have been triggered by a self-Xfunctionality. Therefore, a network operator may see that somethinghappened inside the network but may not receive information about thecause, the root cause or the reason about why something may havehappened within the network. In particular, the network operator may notknow why a self-X functionality may have been executed. In other words,the operator may see that an automated function may have been executedbut may not be able to find out information about the cause of executingor employing that function.

The same may be true for a configuration management, for a networkmanagement or for a network management system (NMS) which may also onlysee an amended network configuration compared with an initial networkconfiguration. But, the NMS may not know the reason for the amendedconfiguration and may believe the amended configuration to be the resultof a malfunction of the network. In that case the NMS could try to healor reconfigure the network configuration in order to reach the initialnetwork configuration. In an example, the NMS and the self-X functioncould work against each other.

Therefore, indicating the reason for amendments may allow an operator ora network management system to understand that an amended networkconfiguration may be the result of a self-X functionality. This mayallow the NMS to ignore an amended configuration.

According to an example the automated function may exclude employing anetwork management system. The network, for example the communicationnetwork or mobile communication network may not involve the networkmanagement system for reconfiguring the network when an amendedsituation may appear.

The network itself, i.e. the network elements themselves or aself-healing server, may try reconfiguring the network without involvinga network management system. Thus, the network management system mayhandle network management objects without taking care about the reasonsfor amendments which may go on inside the network. Thus, on the one handthe load for a network management system may be reduced, however on theother hand, the network may become intransparent for the networkmanagement system. The automated functions or the self-X functions maybe executed without involving the network management system.

According to yet another exemplary embodiment of the present invention,the type of the automated function may be at least one type of a self-Xfunction selected from the group of types of self-X functions consistingof self-configuration, self-optimization of interference coordination,automatic neighbour list management, self-optimization load balancing,self-optimization Interference Coordination, self-optimization of RandomAccess Channel (RACH), self-optimization of capacity, self-optimizationof coverage, self-software management and self-healing.

In an example, Interference Coordination may be adapted to reduce theimpact of interference between at least two neighbor cells.

Automatic neighbor list management (ANR) may be adapted for keeping alist of corresponding neighbor cells up to date. The list mayautomatically be updated by a corresponding self-X function. Forexample, when the installation and commissioning of a new base stationmay be detected, the Automatic Neighbor List Management function may doan up-date of a corresponding list, of a database, of a repository or ofan inventory.

In an example self-configuration may comprise reconfiguring a network toenvironmental conditions, which may have changed.

In another example self-optimization of Interference Coordination (IC)may be provided. Self-optimization Interference Coordination maycomprise adapting interference between communication connections of UEs(User Equipment) or of MSs (Mobile Stations) with Base Stations (BS) toa balanced situation.

In another example load balancing may comprise transferring a user toanother base station or handing over a user, a mobile station or a userequipment to another base station (hand-over) such that connectionswithin the network may be balanced.

Self-optimization of handover parameter may also comprise handing userequipment from one base station to another. In an exampleSelf-optimization of handover parameter may comprise setting-up theconditions for triggering an handover. This may comprise setting up athreshold for triggering handing over of a MS from one base station toanother base station.

In another example the automated function may comprise optimization ofthe random access channel (RACH).

The RACH may be a channel used by user equipment such as a cellularphone or a mobile station for contacting a base station. In a case wherethe number of requests for connections may be higher than the availableresources or channels, not every request may be satisfied. On the otherside, providing too much resources or channels may mean losing too muchbandwidth for actually usable data channels using the same frequency.Thus, RACH optimization may comprise finding a trade-off betweenavailable channels and used bandwidth.

In another example the automated function may comprise optimization of acapacity and/or optimization of coverage.

In yet another example the automated function may comprise softwaremanagement such as a release control or verifying the correct softwareversion.

In another example the automated function may comprise self-healingwhich may allow reacting to a failure situation.

According to another exemplary embodiment of the present invention thestorage area of the record carrier, the parameter or the data structuremay be addressed by a sourceIndicator parameter of at least one methodand/or message selected from the group of methods and/or messagesaccording to the 3GPP standard TS 32.662, the group of methods and/ormessages may consist of a notifyObjectCreation method, anotifyObjectDeletion method and a notifyAttributeValueChange method. Inan example, the method may be a list of parameters and/or an interfacedescription comprising a list of parameters. The corresponding storagearea may be adapted for storing a cause for executing a self-X function.In an example, the cause may be represented by a bit pattern.

An object or managed object may represent stored data or may helpaddressing stored data. An object may allow accessing the stored data ona record carrier or in a memory. The object may allow defining anaddressing scheme for a record carrier, for a computer-readable medium,for a storage or for memory allowing to find information which may havebeen put into the storage.

According to another exemplary embodiment of the present invention, themethod of detecting employing an automated function within a network maycomprise writing information, which may allow specifying the employedautomated function in more details. Such detailed information may bestored in a further predefined storage area of the record carrieraddressable by the object.

An additional storage area for additional information may allow in moredetail describing a cause, a root cause or a reason which may have madenecessary employing or conducting corresponding self-X functionality.The additional storage area may allow providing more detailedinformation to a network management system to inform the networkmanagement system about the reasons for the executed automated function.

According to another exemplary embodiment of the present invention, thefurther predefined storage area may be a further parameter or maycorrespond to a further parameter of at least one method and/or messageof the group of methods and/or messages according to the 3GPP standardTS 32.662 consisting of a notifyObjectCreation method, anotifyObjectDeletion method and a notifyAttributeValueChange method.

A method may be a method according to an object oriented architecture.

According to yet another exemplary embodiment of the present invention,the method may further comprise communicating the informationrepresenting the type of the executed automated function between anAgent Apparatus and a Management Apparatus and/or between an AgentApparatus and a self-X server.

The information can be communicated on the basis of a subscription.Communicating the detailed information may allow informing acorresponding Management Apparatus, an NMS and/or a self-X server aboutthe internal behaviour of the network and about the steps which may havebeen conducted in the network and in addition to the reason why thecorresponding steps may have been conducted. This may make the internalbehaviour of the network more transparent to a Management Apparatus,e.g. to an NMS or to a self-X server. Thus, information may be providedabout the cause which may have triggered reconfiguring the network orexecuting an automated function within the network. Thus, acommunication relationship between the network and administrativeinstances such as network management or self-X server can be establishedin order to clarify the reasons for an actual network configuration.

In an example an NMS may have an initial network configuration and maybe surprised if the initial network configuration may differ ordistinguish from the actual network configuration. In order to clarifythe reasons which may have led to this difference, a communicationrelationship with the network and in particular with an agent inside thenetwork can be established. In an example a manager e.g. an IRPManager(Integration Reference Point Manager) may establish a communicationrelationship with an agent inside the network e.g. an IRPAgent(Integration Reference Point Agent). A communication between the agentand the manager may use an established or subscribed interface, forexample an Itf-N interface. In an example the Itf-N interface may be aninterface between an Agent Apparatus and a Management Apparatus.

According to another exemplary embodiment of the present invention, theAgent Apparatus, e.g. the IRPAgent, may be contained or integrated in atleast one Network Apparatus selected from the group of NetworkApparatuses consisting of an Element Management System (EM), a NetworkElement (NE), a server, a self-healing server or self-healing client, aself-X server or self-X client, a BTS (Base Transceiver Station), an RNC(Radio Network Controller), a NodeB and an eNodeB. In an example theeNodeB may be a macro eNodeB, a home NodeB or femto eNodeB.

The agent and/or the manager may base on at least one standard selectedfrom the group of standards consisting of GSM (Global System for Mobilecommunication), UMTS (Universal Mobile Telecommunication System) and LTE(Long Term Evolution). In particular, the agent and/or manager may useobjects corresponding to the relevant standards.

According to another exemplary embodiment of the present invention, aprogram element may be provided which, when being executed by aprocessor is adapted to carry out at least one method of the method fordetecting employing an automated function within a communication networkand the method for detecting in a Management Apparatus employing anautomated function within a communication network.

In other words, after an automated function may have been executedinformation about the reason or the cause for conducting an automatedconfiguration may be provided by the network in order to transparentlyinform a management system or any other instance which may be interestedabout the internal behaviour of the network.

It has also to be noted that exemplary embodiments of the presentinvention and aspects of the invention have been described withreference to different subject-matters. In particular, some embodimentshave been described with reference to apparatus type claims whereasother embodiments have been described with reference to method typeclaims. However, a person skilled in the art will gather from the aboveand the following description that unless other notified in addition toany combination between features belonging to one type of subject-matteralso any combination between features relating to differentsubject-matters in particular between features of the apparatus claimsand the features of the method claims may be considered to be disclosedwith this application.

These and other aspects of the present invention will become apparentfrom and elucidated with reference to the embodiments describedhereinafter.

Exemplary embodiments of the present invention will be described in thefollowing with reference to the following drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a block diagram of an Agent Apparatus according to anexemplary embodiment of the present invention.

FIG. 2 shows a block diagram of a Management Apparatus according to anexemplary embodiment of the present invention.

FIGS. 3 a to 3 c show different stages of a self-X process according toan exemplary embodiment of the present invention.

FIG. 4 shows a block diagram of a network management architectureaccording to an exemplary embodiment of the present invention.

FIG. 5 shows a message flow diagram for exchanging information of anobject according to an exemplary embodiment of the present invention.

FIG. 6 shows a flowchart of a method for detecting employing anautomated function according to an exemplary embodiment of the presentinvention.

FIG. 7 shows a flowchart of a method for detecting in a ManagementApparatus that an automated function has been employed in acommunication network.

DETAILED DESCRIPTION

The illustration in the drawings is schematic. In different drawings,similar or identical elements are provided with the same referencenumerals.

FIG. 1 shows a block diagram of an Agent Apparatus according to anexemplary embodiment of the present invention.

The Agent Apparatus 100 comprises the Detecting Device 104, the TypeDetermining Device 105 and the Writing Device 108.

The Detecting Device has contact with the network 101 via interfaces 109and 110. In an example the Agent Apparatus is contained in a networkelement, e.g. a network node or a base station, of the network 101. Assymbolically shown with dotted line 111 the Detecting Device 104 is ableto detect the execution or employment of an automated function or of aself-X function inside the network 101. In an example the DetectingDevice detects finishing of an automated function. For example, theDetecting Device is in communicating contact with the self-X server 102which may initiate the self-X functionality inside the network andinform the Agent Apparatus 100 when the self-X functionality has beenexecuted. In other words, the Detecting Device is adapted to monitor thenetwork 101 for amendments.

The Agent Apparatus 100 may be part of the network 101. Via networkinterfaces 109, 110 the Agent Apparatus 100 or network node 100 may bein contact with communication network 101.

In a case where the Detecting Device 104 detects auto-configuration orreconfiguration inside the network 101 the Detecting Device 104 reportssuch an amendment via connection 112 to the Type Determining Device 105.The Type Determining Device is responsible for determining the type ofthe automated function which has been executed. In other words, the TypeDetermining Device detects an indication of a self-X process as reasonfor data change in a network. A data change may be detected when aparameter in a network element have been changed.

Thus, the Type Determining Device may allow identifying which changes ina network were triggered by self-X functionalities. The Type DeterminingDevice can further be adapted to determine the type of an employedself-X functionality and more details about the reasons for executingthe self-x functionality. Examples for different types of self-Xfunctionalities are self-configuration, self-optimization, self-healingand automated software management etc. In other words, as soon as thenetwork itself becomes active concerning the configuration of thenetwork, the activities are registered in the Agent Apparatus.

The Type Determining Device 105 uses the Writing Device 108 for writinginformation representing the type of the automated function, the type ofthe corresponding detected self-X functionality or the cause forexecuting the automated function in a predefined storage area of therecord carrier 103. In an example the record carrier may be a memory, aRAM or an EPROM which may be adapted to receive information from theType Determining Device.

The Writing Device 108 may be controlled by an addressing scheme whichmay be defined as an object model, in order to find the correspondingpredefined position or location of the storage area of a record carrier.FIG. 1 shows an example of a predefined storage area 113. In otherwords, the object definition may be used in order to position theWriting Device to the storage area in order to write the type of thedetected self-X functionality, which was executed within the network101. The Management Apparatus can use the same object model to control aReading Device to the corresponding storage area in order to read-outthe type or cause of the executed self-x function.

The Writing Device and/or the Reading Device may be adapted to access astorage area next to a storage area for storing information aboutadditional text or correlated notifications i.e. a set of notificationsthat are correlated to the subject notification.

The bidirectional link 114 connects the record carrier 103 to theCommunication Device 106 which Communication Device 106 is adapted forcommunicating information representing the type of the automatedfunction between the Agent Apparatus 100 and a Management Apparatus (notshown in FIG. 1) and/or between the Agent Apparatus 100 and a self-Xserver 102. In an example the Communicating Device 106 may comprise aReading Device for accessing a predefined storage area 113 of the recordcarrier 103. For controlling or positioning the Reading Device to accessthe predefined storage area 113 the Communicating Device 106 may use thesame object model as the Writing Device 105. In an example theCommunicating Device, in particular the integrated Reading Device of theCommunicating Device 106 may be controlled by a Management Apparatuswhich may request the information detected by the Detecting Device 104.For communicating with a Management Apparatus or with a NMS theCommunicating Device 106 uses the bidirectional network connection 115which is connected to the communication network 107.

FIG. 2 shows a block diagram of a Management Apparatus 200 according toan exemplary embodiment of the present invention.

The Management Apparatus 200 or NMS 200 comprises a Reading Device 201.The Reading Device 201 of the Management Apparatus 200 in an example cancontrol a Communicating Device 106 in particular an integrated ReadingDevice of an Agent Apparatus 100 (not shown in FIG. 2).

In another example the Reading Device 201 is adapted for reading outinformation representing the type of an automated function from apredefined storage area of a record carrier contained in an AgentApparatus 100. In order to read out the record carrier (not shown inFIG. 2) the Management Apparatus 200 can establish via the bidirectionalnetwork link 202 and via the communication network 107 a connection toan Agent Apparatus 100.

In an example the communication connection 115, 202 may be establishedvia an Itf-N interface. In other words, via the network interface 202,115 or itf-N interface 202,115 the Management Apparatus 200 mayestablish a connection to an Agent Apparatus 100. In other words, theManagement Apparatus 200 may subscribe to an Agent Apparatus 100, to anevent manager or to an event forming instance. In an example theManagement Apparatus is an IRPManager 200 and the Agent Apparatus is anIRPAgent 100.

The Reading Device 201 can determine the type of an automated functionexecuted within a network 101 (not shown in FIG. 2) and can forward thegathered information to the Determining Device 203. The DeterminingDevice 203 is adapted for determining that in a network 101 an automatedfunction has been employed or executed.

For determining that an automated function has been employed inside anetwork 101, the Determining Device 203 uses information read out by theReading Device 201. In other words, the Determining Device can accessthe record carrier 103 of an Agent Apparatus 100. Thus, the DeterminingDevice can be informed about the type of self-X function which has beenemployed inside a network 101. The Determining Device 203 is adapted todetermine that an automated function has been executed in the network101 and/or what type of function has been executed and/or what cause hasbeen the reason for executing the automated function.

The information determined by Determining Device 203 can be communicatedvia the communication port 204, common port 204 or management port 204to another management system 200 a or to a user terminal 205. Thus,either a management system 200 a or an operator can be informed of thetype of self-X functionality which has been executed inside the network101. Thus, an indication of a self-X process as reason for data changeinside the network 101 can be communicated to the user terminal 205 orto an NMS system 200 a. This information may make transparent what isgoing on inside the network 101. Thus, via the communication interface204 information can be provided about activities or amendments insidethe network 101.

In other words, a network operator using the user terminal 205 is ableto identify which changes in his network were triggered by self-Xfunctions.

Table Tab.1 shows an example for a data structure which can be used toaddress a predefined storage area of a record carrier 103. Tab.1 shows anotifyObjectCreation method. This notifyObjectCreation method is anoptional method and may base on the 3GPP standard TS 32.662. An IRPAgent100 notifies an IRPManager 200 about the fact that a new Managed Objecthas been created using the notifyObjectCreation method. The IRPManagermay be subscribed via link 202, 115 and via network 107 to the IRPAgent.Thus, information or notification is sent from the IRPAgent to theIRPManager 200 as soon as the Writing Device 108 has written the type ofthe automated function or the type of the detected self-X function inthe record carrier 103. The type of the self-x function may beassociated with a reason for executing this self-x function. ANotification Header may be a link to parameters of a technical standard.

The creation of a new managed object may only be communicated from theIRPAgent 100 to the IRPManager 200 if the new object satisfy a filterconstraint expressed in an IRPManagers subscribe operation which hasbeen used to establish a communication connection between the IRPAgent100 and IRPManager 200. Table Tab.1 shows input parameters of thenotifyObjectCreation method, of the notifyObjectCreation notification orof the notifyObjectCreation message. Executing the corresponding method(e.g. notifyObjectCreation, notifyObjectDeletion,notifyAttributeValueChange) with the corresponding input parameters,results in sending these parameters as a notification to a manager.

Table Tab.1 comprises four columns. The first column shows a parametername, the second column shows a qualifier, the third column showsmatching information and the fourth column shows a comment. Thus, theparameters or the object description shown in Tab.1 may correspond to anaddressing scheme for the record carrier 103. A predefined storage area103 may correspond to a certain parameter as indicated in column 1 ofTab.1.

A matching information may be a filter parameter which may allowdefining which messages or notification should be visible to a NMS 200,200 a or to an operator 205. This matching mechanism may allowdetermining which information may be written into a log file for onlineor off line processing. The matching information may be a data type forthe corresponding filter.

For example, the notifyObjectCreation comprises an object class whichcan carry the managed entity class name.

In other words, the notificationObjectCreation or notifyObjectCreationmethod, as well as the notifyObjectDeletion and/or thenotifyAttributeValueChange may describe which parameter may be notifiedwhen an Object may be created, deleted or when corresponding attributesmay be amended. This may relate to a notification IRP as described inthe 3GPP standard TS 32.302. The methods may be predefined subscriptionsto an event forming mechanism.

Furthermore, the notifyObjectCreation comprises the parameter objectinstance notificationId, eventTime, systemDN, notificationType,correlatedNotifications.

The optional parameter correlatedNotifications can be used for listingfurther notifications which originate from the same event. Thisinformation about the origin could be used in a self-X function.

TABLE 1 Parameter Matching Name Qualifier Information CommentobjectClass M, Y ManagedEntity.objectClass Notification header. It shallcarry the ManagedEntity class name. objectInstance M, YManagedEntity.objectInstance Notification header. It shall carry the DNof the ManagedEntity. notificationId M, N — Notification headereventTime M, Y — Notification header. It shall carry the ManagedEntitycreation time. systemDN C, Y — Notification header notificationType M, YMapped to a Notification header. notificationTypecorrelatedNotifications O, N — A set of notifications that arecorrelated to the subject notification. additionalText O, N — It cancontain further information in text on the creation of the MO.sourceIndicator O, N ENUM( This parameter, when Resource_operation,present, indicates the Management_operation, source or cause of theSelf_configuration, operation that led to the Self_optimization_IC,generation of this ANR List notification. It can have Management, one ofthe following Self_opt_load values: balancing, 1. resource operation:The Self_opt_HO_parameters, notification was Self_opt_IC, generated inresponse Self_opt_RACH, to an internal Self_opt_Capacity, operation ofthe Self_opt_Coverage, resource; Self_optimization, 2. managementoperation: Self_healing, The notification was Unknown) generated inresponse to a management operation applied across the managed objectboundary external to the managed object; 3. self configuration: Thenotification was generated as result of a self configuration process. 4.self opt_IC: The notification was generated as result of a processdealing mainly with self- optimizaton of Interference Coordination. 5.self opt_load_balancing: The notification was generated as result of aprocess dealing mainly with self- optimizaton of load balancing 6. selfopt_HO_parameters: The notification was generated as result of a processdealing mainly with self- optimizaton of Handover parameters. 7. selfopt_RACH: The notification was generated as result of a process dealingmainly with self- optimizaton of RACH. 8. self opt_capacity: Thenotification was generated as result of a process dealing mainly withself- optimizaton of capacity. 9. self opt_coverage: The notificationwas generated as result of a process dealing mainly with self-optimizaton of coverage. 10. self optimization: The notification wasgenerated as result of a process dealing self- optimizaton (where aallocation to the above mentioned purposes cannot be made) 11. selfhealing: The notification was generated as result of a self-healingprocess. 12. unknown: It is not possible to determine the source of theoperation. attributeList O, N LIST OF The attributes SEQUENCE(name/value pairs) of the <AttributeName, created MO. AttributeValue>

In a sequence starting with objectClass, the notifyObjectCreationcomprises an additionalText parameter following the parametercorrelationNotifications. This additionalText parameter can be anoptional parameter.

In the tables O may be used for indicating an optional parameter, M maybe used for mandatory parameters.

N means that the parameter cannot be used for a filter operation and Ymeans that the parameter can be used for a filter operation.

The additionalTextparameter or additional text parameter can containfurther information in text on the creation of the MO (Managed Object).

A Managed Object is a representation of a real object in a database. Aperson may be represented in an operator database as a subscriberobject. A physical eNodeB (eNB) may be represented by a ManagedObject(MO) eNBfunction.

The parameter additional text may be used for any additional text whichmay not be defined by a standard.

The parameter additional text can for example contain an identifier thatallows identifying which self-X process triggered an event. For example,the object creation, object deletion and attribute value change can bean event.

Furthermore the notifyObjectCreation method comprises a parametersourceIndicator. This is an optional parameter which can have a matchinginformation or a value selected from Resource_operation,Management_operation, Self_configuration, Self_optimization_IC,ANR_list_management, Self_op_t load_balancing, Self_opt_HO_parameters,Self_opt_IC, Self_opt_RACH, Self_opt_capacity, Self_opt_coverage,Self_optimization, Self_healing, unknown.

The sourceIndicator parameter or source indicator parameter when presentindicates the source of the operation that led to the generation of thecorresponding notification (e.g. notifyObjectCreation). The sourceindicator indicates the type of an automated function or a self-Xfunction which have been executed inside a network.

The values resource_operation, management_operation, unknown may beextended or augmented by values of automated functions such as thevalues self-configuration, self-optimization, self-healing, automatedsoftware management, Self_configuration, Self_optimization_IC,ANR_list_management, Self_opt_load_balancing, Self_opt_HO_parameters,Self_opt_IC, Self_opt_RACH, Self_opt_capacity, Self_opt_coverage,self_optimization, Self_healing. Other names of other automated functionmay also be comprised in the source indicator. Thus, the sourceindicator may indicate the source of self-X functionality.

The sourceIndicator can have for example the value Resource_operation.The source indicator has the value Resource_operation, if thenotification was generated in response to an internal operation of theresource.

The sourceIndicator may have the value Management_operation if thenotification was generated in response to a management operation appliedacross the managed object boundary external to the managed object.

The sourceIndicator has the value Self_configuration if the notificationwas generated as a result of a self-configuration process.

The sourceIndicator has the value Self_opt_IC, if the notification wasgenerated as result of a process dealing mainly with self-optimizationof Interference Coordination (IC).

The sourceIndicator has the value Self_opt_load_balancing if thenotification was generated as a result of a process dealing mainly withself-optimization of load balancing.

The sourceIndicator or the type of automated functions may have a valueof Self_opt_HO_parameters if the notification was generated as a resultof a process dealing mainly with self-optimization of Handoverparameters.

The sourceIndicator or type of a self-X function may have the value ofSelf_opt_RACH if the notification was generated as a result of a processdealing mainly with self-optimization of RACH.

The sourceIndicator may have the value of Self_opt_capacity if thenotification was generated as result of a process dealing mainly withself-optimization of capacity.

In an example the sourceIndicator may have the value Self_opt_coverageif the notification was generated as a result of a process dealingmainly with self-optimization of coverage.

The sourceIndicator may have the value Self_optimization if thenotification was generated as a result of a process dealing withself-optimization, where an allocation to the above-mentioned purposescannot be made.

The sourceIndicator may have a value or type of Self_healing if thenotification was generated as a result of a self-healing process.

The sourceIndicator may have a value of unknown if it is not possible todetermine the source of an operation.

Thus, the value of sourceIndicator represents the source of operation,i.e. the name of the type of operation.

Furthermore, the notifyObjectCreation method may comprise a parameterattributeList which is a list of a sequence comprising AttributeName andAttributeValue for the attributes (name/value pairs) of the created MO.Example for name and/or value pairs may be forename and surname of asubscriber of a network operator.

Self_configuration could mean bringing a new eNodeB in the field andproviding the eNodeB automatically with commissioning parameter.

An example for Self_opt_IC could comprise detecting interferences on afrequency and determining the cause for the interference in a neighborcell. This may be done by reducing the transmission power. As all self-Xfunctions, the Self_opt_IC functions without involving the NMS, i.e.substantially any communication via the Itf-N interface may be preventedfor executing a self-X function.

Self_opt_load_balancing can comprise regularly receiving an alarmmessage reporting an overload situation of a cell. Free capacities of aneighbor cell can be used by reducing an angle of the antenna of theoverloaded cell and thus reducing the footprint of the cell. The loadmay be reduced since the footprint of the cell may be reduced and loadmay be taken over by neighbor cells having free capacity.

The Self_opt_HO_parameter for indicating that HO optimization has beenexecuted. HO optimization can be used if a handover statistic shows thatin a region, e.g. at the border of two cells, a so called “ping-pong”handover is regularly executed. A MS or mobile phone regularly changesthe connection from one base station to another. A self-X functionalitycan for example increase a hysteresis for the handover threshold inorder to prevent this ping-pong handover.

Self_opt_capcaity could be employed if not all available channels areused. A reason for not using all channels may be saving energy. However,if in a corresponding cell the number of users has been increasedadditional channels of the unused channels could be activated.

Self_opt_coverage could be executed if measurements show that some areasare not covered by radio signals of cells and therefore, in these areasreceiving radio signals is not possible. The self-X functionalitySelf_opt_coverage can react with increasing the transmitting power of abase station. The self-X functionality or the network decides about howto react on its own. A communication via an Itf-N interface or a networkmanagement system interface can be prevented.

The Self_opt_RACH functionality could detect that the available RACHchannels are not fully occupied. Thus, employing the Self_opt_RACHfunctionality can result in using at least one of the light loaded RACHchannels as a data channel.

A Self_healing functionality can reconfigure neighbor cells in order toreplace a defective or failed cell. When a cell fails in the neighborcell the transmit power may be increased and/or the angle of an antennacan be reduced such, that the footprint of the failed cell may besupplied substantially by the adapted cell. Self healing will bedescribed in more detail in FIGS. 3 a-3 b.

Using the different values for parameter sourceIndicator may allowidentifying the source of a self-X functionality. The different valuesmay be represented by different bit patterns. In other words, the sourceindicator may allow identifying which changes in the network weretriggered by self-X functionalities.

Table Tab.2 shows input parameters of a notifyObjectDeletion method. Theinput parameters or the list of input parameters comprise in accordancewith the notifyObjectCreation method the additional text parameterand/or the source indicator parameter as defined in table Tab. 1.

The IRPAgent 100 notifies the subscribed IRPManager 200 of a deletedmanaged object using the notifyObjectDeletion method. The managedobjects represent real physical objects such as subscriber of a networkoperator. A subscriber object may be created when the subscribersubscribes to an operator and may be deleted when the subscriberwithdraws the subscription. Managed objects can be created, changedand/or deleted by using the corresponding method. The method may beutilized by an agent and/or by a manager. The agent and/or manager canbe controlled by rules.

The IRPAgent invokes the notifyObjectDeletion notification because thesubject notification satisfies a filter constraint expressed in theIRPManager subscribe operation. This notification is sent from theIRPAgent 100 to the IRPManager 200.

TABLE 2 Matching Parameter Name Qualifier Information CommentobjectClass M, Y ManagedEntity.objectClass See Tab. 1 objectInstance M,Y ManagedEntity.objectInstance See Tab. 1 notificationId M, N — See Tab.1 eventTime M, Y — Notification header. It shall carry the ManagedEntitydeletion time. systemDN C, Y — See Tab. 1 notificationType M, Y Mappedto a See Tab. 1 notificationType. correlatedNotifications O, N — SeeTab. 1 additionalText O, N — See Tab. 1 sourceIndicator O, N See Tab. 1See Tab. 1 attributeList O, N LIST OF SEQUENCE The attributes<AttributeName, (name/value pairs) AttributeValue> of the deleted MO.

When a managed object is deleted, all subordinate Managed Objects, i.e.the complete sub-tree of a MIB, are also deleted. Furthermore, allassociations where the Managed Object participates are deleted.

Table Tab.3 shows the input parameters of a notifyAttributeValueChangemethod. The use of the notifyAttributeValueChange method may beexplained using an example of the self-X process or the self-X functionSelf_opt_coverage. The Self_opt_coverage process in the example triggersincreasing the physical transmit power of a physical eNodeB. Thephysical eNodeB is represented by associated objects. In the case ofincreasing the transmit power of an eNodeB a value of a parameterrepresenting the transmit power in an associated eNBfunction object maybe changed. This change in the eNBfunction is notified using thenotifyAttributeValueChange, when the change have been detected.

TABLE 3 Matching Parameter Name Qualifier Information CommentobjectClass M, Y ManagedEntity.objectClass See Tab. 1 objectInstance M,Y ManagedEntity.objectInstance See Tab. 1. notificationId M, N — SeeTab. 1 eventTime M, Y — Notification header. It shall carry theattribute(s) value(s) changed time. systemDN C, Y — See Tab. 1notificationType M, Y Mapped to a See Tab. 1 notificationType.correlatedNotifications O, N — See Tab. 1 additionalText O, N — See Tab.1 sourceIndicator O, N See Tab. 1 See Tab. 1 attributeValueChange M, NLIST OF SEQUENCE The changed <AttributeName, attributesNewAttributeValue, (name/value pairs) of CHOICE [NULL, the MO (with bothnew OldAttributeValue] and, optionally, old > values).

The notifyAttributeValueChange method also comprises the additional textparameter and/or source indicator as described in table Tab.1. Thestructures of the notifyObjectCreation, the notifyObjectDeletion and thenotifyAttributeValueChange method correspond to each other.

The IRPAgent 100 notifies the subscribed IRPManager 200 about a changeof one or several attributes of a managed object in the NRM (NetworkResource Model). The NRM is a description or definition of objects, thecontent of the objects and the relations between the objects. TheIRPAgent 100 invokes the notification because the subject notificationsatisfies a filter constraint expressed in the IRPManager 200 subscribeoperation. The filter mechanism can be integrated in the Writing Deviceof an agent and/or in the Reading Device of a manager.

The definition of the parameter additional text as of Tab.1, Tab.2 andTab.3 used in notifications notifyObjectCreation, notifyObjectDeletionand notifyAttributeValueChange may be extended to the description thatthe parameter additional text can e.g. contain an identifier that allowsidentifying which self-X process triggered the event.

In an alternative example the additional text parameter could be used tointroduce a specific new parameter or a further parameter to indicate anidentifier that allows identifying which self-X process triggered theevent. Thus, a separate parameter may be added to table Tab.1, Tab.2and/or Tab.3 which can e.g. contain an identifier that allowsidentifying which self-X process triggered an automated function.

An object as defined in 3GPP TS 32.662 may be reused.

For notifyObjectCreation, notifyObjectDeletion and/ornotifyObjectAttributeValueChange notifications which are triggered by aself-configuration functionality the value Self-configuration shall beused for the input parameter sourceldentifier.

FIGS. 3 a to 3 c show employing a self-X process in a network accordingto an exemplary embodiment of the present invention.

FIG. 3 a shows a scenario where seven different cells 301, 302, 303,304, 305, 306, 307 generate a communication network 101 or a footprintof a cellular communication network. In other words, the seven cells 301to 307 are generated by seven antennas of base stations if all antennasand/or all base stations are working. In the following the terms celland base station may be similarly used.

FIG. 3 b shows the network scenario 101 of FIG. 3 a where one basestation 307 has failed according to an exemplary embodiment of thepresent invention. In FIG. 3 b the middle base station (BTS) 307 hasfailed. The failure of base station 307 generates an area 307 which isnot covered any more.

FIG. 3 c shows a network configuration after executing or employing aself-X function according to an exemplary embodiment of the presentinvention.

The failure in the network 101 has been detected. For example, a self-Xserver, not shown in FIG. 3 a, 3 b, 3 c has detected that BTS 307 orcell 307 has been failed. By using self-healing functionalities,self-healing functions or self-healing processes the shape of cells301′, 303′, 305′ has been adapted such, that the amended shape of thecells now also covers the failed middle cell 307. Self-healing couldalso be combined with self-configuring. This self-healing or activationof a replacement configuration has been conducted by the network 101itself or by a corresponding self-healing server 102. A networkmanagement system 200 however, may not be informed about theself-healing functionality. The NMS may not be involved in reconfiguringthe network 101.

By reading-out the record carrier 103 of a corresponding Agent Apparatusin the network 101 the NMS can identify that self-healing has beenexecuted and that self-healing was the cause for the amended networkconfiguration.

Thus, the informed NMS may not try to change the configuration, sincethe NMS understands that this was generated by a required self-healingoperation in order to cover the missing middle cell 307.

In other words, in the scenario as shown in FIGS. 3 a to 3 c, the cellsor radio cells 301 to 307 cover a predefined geographical area. In thecase of FIG. 3 a every station 301 to 307 covers a substantially equallysized area.

FIG. 3 b shows the failing of one antenna 307 of the cells 301-307. Aself-healing server 102 is informed about failing of cell 307. Theself-healing server or self-X server 102 has a replacement configurationfor such failure scenarios and activates one of the replacementconfigurations without involving a network management system 200 (NMS).Thus, for executing self-healing exchanging messages via an Itf-Ninterface substantially be prevented.

This NMS 200 and/or all other NMSs 200 a, 200 b are informed by anotification having the parameter sourceIndicator set to self_healing(sourceIndicator=self-healing). In other words, annotifyAttributeValueChange method may be invoked with sourceIndicatorset to self_healing. This method informs an NMS or an IRPManager 200about the configuration amendment of every single cell. ThesourceIndicator value informs an NMS or an IRPManager 200 about theemployment of the self-X function in the network 101. In order to allowthat an NMS knows that the single messages of every reconfigured cellbelong to the same event, the correlated notifications of the differentcells may be listed in the correlatedNotifications parameter of theinvolved notifications.

The failure of cell 307 can additionally be reported by an alarmnotification.

This may prevent the NMS to regard the configuration change in everysingle cell 301 to 307 as independent and as a violation of a certainconfiguration policy (e.g. to a policy requiring not to set transmissionpower higher than a certain value during normal operation). An NMS,which is responsible for the handling of failures, thus has not toinform the other NMS in order to amend the configuration. Thus the NMSsmay not receive a notification with source indicator set tomanagement_operation.

Since the amendments have been conducted inside the network and were nottriggered by a network management, it is also prevented that the NMSstry to reconfigure the cells 301 to 306.

Thus using the sourceIndicator parameter set to self_healing allowsshowing to the NMS 200 that without involvement of a network managementsystem the error, i.e. the failed antenna 307, has been handled by aself-healing server 102. This may also prevent that one of the NMSs forexample detects the amended configuration of FIG. 3 c and may determinea failure in a parameter-policy and may try to reconfigure the scenarioshown of FIG. 3 c. Every NMS may be informed via the sourceIndicatorparameter that the configuration shown in FIG. 3 c was initiated by thenetwork which has determined that the configuration has been changed.

FIG. 4 shows a block diagram of a network management architectureaccording to an exemplary embodiment of the present invention.

The Agent Apparatus 100 comprises the element management system (EMS)401 and the network element (NE) 400. The EMS and the NE are incommunicating connection 402. The agent 100 may be part of acommunication network 101 (not shown in FIG. 4). The self-X server 102,e.g., a self-healing server, is connected via the communication link 403to the EMS 401.

Furthermore via an Itf-N interface 404 the NMS systems NMS1 200, NMS2200 a and NMS n 200 b are connected to the agent 100 or to the EMS 401.

FIG. 5 shows a message flow diagram for exchanging information of anobject according to an exemplary embodiment of the present invention.

The plurality of NEs 400 of a communication network 101, are representedby one NE 400. NE 400 in step S500 sends an alarm message to an EMS 401,in order to inform EMS 401 that an antenna has failed, for example theantenna of cell 307. EMS 401 in step S501 forwards the alarm messagefrom NE 400 to the self-X server 102, for example the self-healingserver 102. The EMS 401 in step S502 sends the same alarm message of NE400 about failing of antenna 307 to at least one NMS 200 of the group ofNMSs 200, 200 a, 200 b.

After the receipt of the alarm message of step S501, in step S503 theself-X server 102 determines that failing of the antenna 307 can behandled by the self-X server 102.

In step S504 the self-X server 102 sends information to the NMS 200 thatthe self-X server handles the replacement configuration of the failedantenna in the network represented by NE 400. The message sent fromself-X server 102 to NMS 200 may comprise an identifier X. The NMS doesnot care about handling the failure and therefore no further informationis sent to the NMS 200 via Itf-N interface while the self-X server 102organizes the reconfiguration in the network 101.

In step S505 the self-X server 102 determines the replacementconfiguration and in step S506 the self-X server 102 sends thereplacement configuration for a plurality of NEs 400 to the EMS 401. Thereplacement configuration comprises the identifier X.

The EMS 401 determines the replacement configuration for each NE 400 andsends the corresponding replacement configuration to each individual NE400 (step S506′). Thus, the self-X server 102 manages the replacementconfiguration of network 101 by informing corresponding NEs 400 about anew configuration.

In step S507 the EMS 401 or the Agent Apparatus 100 sends a createmessage, a delete message and a change message, respectively(create/delete/change message) comprising sourceIndicator set toself-healing including—in the parameter additionalText—the identifier Xto the self-X server 102.

The identifier X may identify an event with a unique ID or with a uniqueevent number. A configuration-NMS and/or an application assessinglog-files can use the identifier X to determine that amendments in thecells 301 to 306 and/or NEs 400 correspond to each other or are based onthe same cause. The identifier X could also be used for requesting orreading-out information about the events that were caused by the processand/or event having the identifier X. Further information such asduration of the triggered events, duration of the self-healing processetc. could also be stored or read-out.

The self-X server 102 receives the corresponding message or list ofparameters as an answer, acknowledge or response to the replacementconfiguration sent in step S506.

In parallel to the create/delete/change message, the EMS 401 in stepS508 sends the create/delete/change message to the NMS 200. The NMS 200receives the corresponding message or list of parameters as aninformation or update message, in order to inform the NMS 200 about theactual configuration or status of the network. In an example, the NMS200 is informed about the cause for the self-healing function.

In other words, the list of parameters as described in tables Tab. 1 toTab. 3 may be sent to the self-x server 102 and/or to the NMS 200. Thecreate/delete/change message can be used as acknowledge message or as aninformation message.

FIG. 6 shows a flowchart of a method for detecting employing anautomated function according to an exemplary embodiment of the presentinvention.

The method starts in the idle state 5600.

In step S601 the execution of an automated function inside acommunication network is detected.

Step S602 comprises determining the type of the corresponding automatedfunction.

The information representing the type of the automated function in stepS602 is written in a predefined storage area of a record carrier beforein step S604 the method returns to the idle state.

FIG. 7 shows a flowchart of a method for detecting in a ManagementApparatus that an automated function has been employed in acommunication network.

The method starts in the idle state 5700.

In step S701 a request for a reason for a network configurationamendment is made by reading-out information representing the type ofthe automated function of a predefined storage area of a record carrier.

In another example, no request has to be made since a message containingthe required information or list of parameters is received.

If a configuration NMS, i.e. an NMS responsible for configuring anetwork, needs to know who or which was a trigger for a detectedamendment, a record carrier could be read-out. Self-X functions, inparticular self optimizing self-X functions may do not use alarmmessages or alarm notifications. Thus, a read-out or a request from arecord carrier can be utilized to receive information about the cause ofan amendment, which otherwise only would be available to the NMS 200 ifan alarm message was generated.

Thus, the record carrier can be used as a “letter box” to exchangemessages between an NMS 200 and a network 101, in particular to exchangethe type of a self-X function employed in a network 101.

In step S702 the employment of an automated function for reconfiguringthe network is determined using the information which was read-out instep S701.

In step S703 the idle state is reached again waiting for the nextoperation.

It should be noted that the term “comprising” does not exclude otherelements or steps and the “a” or “an” does not exclude a plurality. Alsoelements described in association with different embodiments may becombined.

It should also be noted that reference signs in the claims shall not beconstrued as limiting the scope of the claims.

Acronyms and Terminology CM Configuration Management MIB ManagementInformation Base

OAM Operation, Administration, Maintenance

1. Method for detecting employing an automated function comprising:detecting the execution of an automated function within a communicationnetwork; determining a type of the automated function; writinginformation representing the type of the automated function in apredefined storage area of a record carrier.
 2. Method of claim 1,wherein the automated function excludes employing a Network ManagementSystem.
 3. Method of claim 1, wherein the type of the automated functionis at least one type of a self-X function selected from the group oftypes of self-X functions consisting of Self-configuration;Self-optimization of Interference Coordination; Automatic Neighbour ListManagement; Self-optimization load balancing; Self-optimizationInterference Coordination; Self-optimization of Random Access Channel;Self-optimization of capacity; Self-optimization of coverage;Self-Software-Management; and Self-healing.
 4. Method of claim 1,wherein the storage area is addressed by a sourceIndicator parameter ofat least one method and/or message selected from the group of methodsaccording to the 3GPP standard TS32.662, the group consisting of anotifyObjectCreation method, a notifyObjectDeletion method and anotifyAttributeValueChange method.
 5. Method of one of claim 1, furthercomprising: writing in a further predefined storage area of the recordcarrier information, which allows specifying the automated function. 6.Method of claim 5 wherein the further predefined storage area is afurther parameter of at least one method and/or message of the group ofmethods according to the 3GPP standard TS32.662 consisting of anotifyObjectCreation method, a notifyObjectDeletion method and anotifyAttributeValueChange method.
 7. Method of one of claim 1, themethod further comprising: communicating the information representingthe type of the automated function between an Agent Apparatus and aManagement Apparatus and/or a Self-X Server.
 8. Agent Apparatuscomprising: a Detecting Device for detecting the execution of anautomated function within a communication network (101); a TypeDetermining Device for determining the type of the automated function; aWriting Device for writing information representing the type of theautomated function in a predefined storage area of a record carrier. 9.Agent Apparatus of claim 6, wherein the Agent Apparatus is contained inat least one network apparatus selected from the group of networkapparatuses consisting of an Element Management System; a networkelement; a server; a self-x server; a self-healing server; a BTS; anRNC; a NodeB; and an eNodeB.
 10. Method for detecting in a ManagementApparatus employing an automated function within a communicationnetwork, the method comprising: reading-out information representing thetype of the automated function of a predefined storage area of a recordcarrier; determining employing an automated function using the readoutinformation.
 11. Management Apparatus comprising: a Reading Device forreading-out information representing the type of the automated functionof a predefined storage area of a record carrier; a Determining Devicefor determining employing an automated function using the read-outinformation.
 12. Computer readable medium, comprising program code,which, when being executed on a processor is adapted to carry out atleast one method of the method for detecting employing an automatedfunction within a communication network of claim 1; and the method fordetecting in a Management Apparatus employing an automated functionwithin a communication network, the method comprising: reading-outinformation representing the type of the automated function of apredefined storage area of a record carrier; determining employing anautomated function using the readout information.
 13. Data structure ofthe 3GPP standard TS32.662, comprising at least one predefined parameterfor storing a type of an automated function within a network; whereinthe parameter can be addressed by an address scheme based on an objectdefinition.
 14. Record carrier, comprising a storage area for storing atype of an automated function within a network; wherein the storage areacan be addressed by an address scheme based on an object definition. 15.Use of an object according to the 3GPP standard TS32.662 for storing atype of an employed automated function on a predefined storage area of arecord carrier.